Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1230

reference
362-tree-1
name
1230
tree-preservation-order

undefined

362-tpo-1
uprn
address-text
point
POINT (-1.035163 50.897798)
geometry
MULTIPOLYGON (((-1.035120 50.897793,-1.035122 50.897802,-1.035128 50.897809,-1.035137 50.897815,-1.035149 50.897819,-1.035162 50.897821,-1.035175 50.897820,-1.035187 50.897816,-1.035197 50.897810,-1.035203 50.897802,-1.035205 50.897794,-1.035203 50.897786,-1.035197 50.897778,-1.035188 50.897772,-1.035176 50.897768,-1.035163 50.897767,-1.035150 50.897768,-1.035138 50.897772,-1.035128 50.897778,-1.035122 50.897785,-1.035120 50.897793)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL